fix: redirection based on location header for methods other than HEAD #1410
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Could you give me a little bit more context of why it is needed or with which server you are encountering an issue that can motivate this change? Because from my point of view, the kind of "redirection" that we are looking for are supposed to be "application data" that is in the body, and so, if we don't have a data and that it is not a HEAD request, it might probably mean that we are not targeting a wrong service or endpoint. |
|
@fviard, redirection is not always initiated by a s3 system, it could be initiated by gateways, etc. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The location header can be provided with methods other than HEAD.